home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 20
/
Cream of the Crop 20 (Terry Blount) (1996).iso
/
bbs
/
ra_p250.zip
/
RADEMO.ARJ
/
RA250B.RAD
/
READ.ME
< prev
next >
Wrap
Text File
|
1996-05-01
|
6KB
|
147 lines
RemoteAccess 2.02 documentation corrections.
--------------------------------------------
Copyright 1989-1994 Wantree Development & Andrew Milner, All Rights Reserved.
This file documents changes to the software that were made after the manual
went to print. THERE ARE ADDITIONAL CHANGES DOCUMENTED IN WHATSNEW.202!
JAM message-base support
------------------------
In order for JAM support to function correctly, you *MUST* have SHARE
loaded. If you are unsure how to do this, check your DOS manual.
RIP Support
-----------
This version of RemoteAccess has support for the online graphical protocol
RIP (Remote Imaging Protocol). To give your BBS RIP functionality, simply
create the appropriate RIP screens in your textfile directory. RemoteAccess
will auto-detect RIP at the user's end and display the .RIP files (where
available) in preference to your regular ASC/ANS/AVT textfile.
An indicator on the F1 status bar signals the sysop that RIP is currently
active. Additionally, a boolean flag has been added to the EXITINFO.BBS
drop-file so that doors and other external programs can determine whether
the user's terminal supports RIP.
NOTE that RIP graphics are never displayed locally. Instead, a window will
pop up during the display of a RIP file to indicate what the user is seeing.
RAMSG.EXE
---------
Command-line parameters specific to JAM areas are not documented in the
manual. The following notes apply to the JAM support in RAMSG:
* A number of RAMSG options and command-line parameters do not apply to JAM
areas, and are therefore ignored. Note that the following options are still
valid for Hudson areas, as per the documentation:
RAMSG INDEX - The "delete" and "recover" options are ignored for JAM areas.
RAMSG PACK - The "force", "overwrite", "delete" and "recover" options
are ignored for JAM areas.
* It should also be noted that JAM areas will ONLY be linked if the -Link
option is specified during a PACK operation. This is not true of Hudson
areas, whose reply links are always updated.
* A number of command-line switches have been added to RAMSG:
-JAM - Process JAM areas only.
-Hudson - Process Hudson areas only.
-NoLrdPack - Disables packing of lastread pointers in JAM areas.
-Unused - (With PURGE) deletes all messages in any undefined Hudson areas.
* While there are no limits per se on the number of messages in a JAM area,
this version of RAMSG can only handle a maximum of 65,535 messages per JAM
area. RAMSG will require more or less memory depending on the size of the
message-base to be packed. Memory required is approximately 64k + 8 bytes
per message. This means that on a machine with 590k available, RAMSG can
easily process the maximum number of messages (65,535).
Page 3-76
---------
The description for menu type 51 should read:
This function displays a list of all users who have
logged-on to your system since midnight, showing
log-on/log-off times, connection speed, what node (line)
the user was logged-on to, number of calls placed, and
the location of the user. If the optional /H parameter
was specified, user handles are displayed in place of
real names.
Page 4-10
---------
In the "system data codes" list, code number 93 is incorrectly listed
as ^K[nnn. The correct code is ^K]nnn.
In the "User Data Codes" paragraph, ^FO is incorrectly identified as
displaying either On or Off for the users full screen editor. ^F0 is
the correct control code for this function. ^FO is the users security
level.
Page 4-16
---------
The external support file FGR#####.A?? is missing from this page. This
file is equivalent to the MGR#####.A?? file, except is applies to file
areas.
Page 4-24
---------
The external support textfile VIP.A?? is missing from this page. This
file is displayed upon logon to all users listed in the VIP.CTL file.
Page 6-8
--------
One of the examples is incorrect. The example which reads
"RAMSG INDEX -Delete -Recover -Renumber" should read
"RAMSG INDEX -Delete -Recover".
The errorlevels for RAMSG are documented incorrectly. The correct
errorlevels are:
251 Configuration file version ID mismatch
252 Incorrect DOS version
253 Insufficient disk space available
254 Insufficient memory available
255 Disk error or missing configuration data
3 Fatal error detected by Borland C++ Start Up Code
(Usually this means there is insuffient memory to set up a stack)
0 No errors occurred
Page 7-16
---------
The last paragraph incorrectly makes a reference to RAFILE. This should
actually refer to RAMGR.
Page 7-22
---------
The paragraph following the field list incorrectly states that <Enter>
should be pressed when editing is complete; the correct keystroke is
<Escape>
Page 9-10
---------
The "LastCl" screen has two undocumented sub-options; pressing 'N' toggles
between real names and handles, and 'T' activates track mode. When track
mode is active (any other key disables track mode), the highlight bar is
automatically kept on the most recent entry in the lastcall list at all
times.
Page 11-22
----------
The first paragraph incorrectly states that the FrontDoor mailer is
published by Advanced Engineering sarl, when it is actually published
by Joaquim Homrighausen.